Multiple device and multiple line connected home and home monitoring

ABSTRACT

Systems, devices, and techniques for multiple device and multiple line enabled computing devices and computing appliances are described herein. A device number can be assigned to a computing device and can be unique to the computing device. A plurality of alias numbers can be provided to the computing device and enabled for use by the computing device. Alias numbers can be enabled on multiple computing appliances, such that a user can transfer voice or video calls between devices using the alias numbers. Further, monitoring components in a home environment, for example, can be associated with one or more alias number so that security alerts can be provided to the various computing devices and computing appliances associated with the alias numbers.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is a continuation of and claims the benefit ofU.S. patent application Ser. No. 15/062,964, filed on Mar. 7, 2016,entitled “MULTIPLE DEVICE AND MULTIPLE LINE CONNECTED HOME AND HOMEMONITORING”, which is hereby incorporated in its entirety by reference.

BACKGROUND

A computing device, such as a wireless phone, that is capable ofterminating (e.g., receiving) or originating phone calls is typicallyassociated with one particular phone number. The computing device canonly terminate phone calls whose called number is the particular phonenumber. Thus, someone with, for example, multiple businesses can have tocarry multiple computing devices, because each of the computing devicesis associated with a different phone number. Not only is this cumbersomefor the user, but wasteful because the user has to acquire multiplecomputing devices, one computing device per phone number.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 illustrates an example environment in which multiple device andmultiple line enabled computing devices and computing appliances caninitiate and transfer communications, in accordance with embodiments ofthe disclosure.

FIG. 2 illustrates an example environment in which home monitoring isprovided by extending the functionality of the multiple device andmultiple line environment, in accordance with embodiments of thedisclosure.

FIG. 3 illustrates an example computing device configured with themultiple device and multiple line functionality, in accordance withembodiments of the disclosure.

FIG. 4 illustrates an example network provider configured to operate inthe multiple device and multiple line environment, in accordance withembodiments of the disclosure.

FIG. 5 illustrates an example process for initiating and transferring acommunication in the multiple device and multiple line environment, inaccordance with embodiments of the disclosure.

FIG. 6 illustrates an example process for monitoring a home location andproviding alerts in the multiple device and multiple line environment,in accordance with embodiments of the disclosure.

DETAILED DESCRIPTION

The systems, devices, and techniques described herein present frameworksfor routing audio and/or video calls within a multiple device andmultiple line environment, as well as extending the environment toprovide home monitoring.

When a user acquires a computing device, such as a wireless phone, awireless service provider or network provider can assign anInternational Mobile Subscriber Identity (IMSI) and/or an E.164 address(e.g., up to a fifteen digit telephone number) that is specific for theuser associated with the computing device. As used herein, a “devicenumber” is the E.164 address or identity assigned (such as an IMSI, or aMobile Station International Subscriber Directory Number, MSISDN) to thecomputing device by the wireless service provider or network provider.

Computing devices can be associated with one or more additional aliasnumbers that can be activated or installed at various computing devicesand/or computing appliances. For example, a first computing device canbe associated with a first device number and various alias numbers(e.g., Alias #1, Alias #2, Alias #3, etc.), while a second computingdevice can be associated with a second device number and various aliasnumber (e.g., Alias #1, Alias #2, Alias #4, etc.). Thus, the firstcomputing device and the second computing device represent the multipledevice and multiple line functionality described herein, whereby asingle number can be associated with multiple devices, and whereby asingle device can be associated with multiple lines. Further, computingappliances can be configured with client applications supporting one ormore alias numbers (e.g., Alias #1, Alias #2, Alias #3, Alias #4, etc.).

A communication (e.g., a voice call, a video call, SMS, MMS, etc.) canbe initiated at a computing device via the device number associated withthe computing device or via an alias number. Considering animplementation in a home context, a user can initiate a voice call on acomputing device and may wish to transfer the call to another computingdevice or computing appliance located throughout the home of the user.The user can configure the communication to remain on the same line(e.g., associated with the device number) or can configure thecommunication to switch to a new line (e.g., associated with anotherdevice number or an alias number). The user can initiate the transfer onthe computing device and can use a transfer module at a computingappliance (e.g., via a graphical user interface presented on a displayor via a voice interface presented using an audio system) to pick up thecall as the user moves about the home. Thus, the user can extend thefunctionality of the multiple device and multiple line environment totransfer communications between various computing devices and/orcomputing appliances configured to interface with the various devicenumbers and/or alias numbers.

It can be understood in the context of this disclosure that devicenumbers and alias numbers can be associated with any number of computingdevices and/or computing appliances. In some embodiments, a networkprovider can maintain registration tables associating the various devicenumbers and alias numbers with various computing devices and computingappliances. Thus, the network provider can route communicationsaccording to the registration tables as described herein. Further,communications can be initiated on computing devices or computingappliances, using one or more device numbers and/or alias numbers.Communications can be transferred among any device numbers and/or aliasnumbers, as described herein.

Various monitoring components (e.g., home security components) can beintegrated into the multiple device and multiple line environment toprovide monitoring capabilities. For example, a home can be equippedwith a video conferencing system that is associated with one or morealias numbers. By way of example, when the video conferencing system isoperated, a video camera and/or intercom can route a communication(e.g., an IR. 94 IMS conservational video communication) to one or morecomputing devices and/or computing appliances associated with the aliasnumbers. Thus, when the video camera is initiated, the video call can berouted to multiple computing devices, for example, such that any one ofthe multiple computing devices can receive the video call. In someembodiments, unique rules can be associated with the various monitoringcomponents. By way of example, a picture message (e.g., MMS) can be sentto particular device numbers or alias numbers when a doorbell isactivated, while a text message can be sent to another set of devicenumbers or alias numbers when a window sensor is activated. Thus, themultiple device and multiple line functionality can be incorporated withmonitoring components to provide home security, for example.

In this manner, the systems, devices, and techniques described hereinimprove a functioning of a computing device by optimizing communicationrouting to desired computing devices and computing appliances. Forexample, the systems, devices, and techniques described herein canreduce duplicative devices and enable communications to be received atdevices without being constrained to a particular device.

The systems, devices, and techniques described herein can be implementedin a number of ways. Example implementations are provided below withreference to the following figures.

FIG. 1 illustrates an example environment 100 in which multiple deviceand multiple line enabled computing devices and computing appliances caninitiate and transfer communications, in accordance with embodiments ofthe disclosure. In some embodiments, communications (e.g., voice and/orvideo data) can be initiated and transferred between the variouscomputing devices 102 and 104 and various computing appliances 106, 108,and 110, in accordance with the routing provided by network provider(s)112.

In general, a communication can be initiated via any one of thecomputing devices 102 and 104 and the computing appliances 106, 108, and110. In one example, if a user initiates a communication using thecomputing appliance 106 and an alias number, the user can transfer thecommunication to another computing appliance associated with the aliasnumber, such as the computing appliance 110, as the user movesthroughout the location 114.

The computing devices 102 and 104 can be any sort of device capable ofengaging in wired or wireless communication with other, remote devices.Thus, computing devices 102 and 104 can include, but are not limited to,smart phones, mobile phones, cell phones, tablet computers, portablecomputers, laptop computers, personal digital assistants (PDAs),electronic book devices, or any other portable electronic devices thatcan generate, request, receive, transmit, or exchange voice, video,and/or digital data over a network. Example networks carrying callsinclude second-generation (2G), 3G, or fourth-generation (4G) cellularnetworks, such as LTE (Long Term Evolution) via VoLTE (Voice Over LTE)using SIP (Session Initiation Protocol) signaling, and data networks,such as Wi-Fi networks carrying VoIP (Voice Over Internet Protocol)calls.

In some embodiments, the computing device 102 can include a nativedialer 116, a client application 118, device number(s) 120, aliasnumber(s) 122, and user interface(s) 124. In some embodiments, thenative dialer 116 can be an application that enables calls to beoriginated via Voice over Internet Protocol (VoIP), circuit switchedvoice, or some other protocol, using Session Initiation Protocol (SIP)signaling. In some embodiments, the native dialer 116 can be configuredto initiate communications using the device number(s) 120. In someembodiments, the device number(s) 120 can correspond to an E.164 addressor identity assigned (such as an IMSI) to the computing device by thenetwork provider 112. For example, the device number 120 can correspondto a phone number such as “555-111-2222”.

In some embodiments, the client application 118 can permit a user toinitiate or terminate calls for other phone numbers in addition to thedevice number(s) 120. For example, the client application 118 can enablecommunications using the alias number(s) 122. In some embodiments, thealias numbers 122 can include phone numbers or other identifiersallocated by the network provider 112 for use in connection with thedevice numbers 120. However, in some embodiments, the alias numbers 122are not associated with any computing devices (e.g., via a SubscriberIdentity Module, SIM card, or via a Removable User Identity Module,R-UIM, etc.) or computing appliances until a particular alias number isactivated for use at the computing device or computing appliance. Thus,a user can use the client application 118 to activate the alias number122 at the computing device 102, for example, and the client application118 can be used to initiate calls and transfer calls to and from thevarious alias numbers 122. Further, the client application 118 oranother application or interface provided by the network provider 112can permit the user to select, enter, or view the alias numbers 122, orto add descriptions for the alias numbers, such as “personal,” “work,”“school,” “refrigerator,” “television,” “smart mirror,” etc.

In some embodiments, the user interfaces 124 can include any displays,haptic feedback or input, and/or audio systems to interface with thecomputing device 102. For example, the user interface 124 can initiate acall via the native dialer 116 and/or the client application 118,transfer a call to another computing device or computing appliance, andreceive a call from the environment 100.

In some embodiments, the computing device 104 can include a nativedialer 126, a client application 128, device number(s) 130, aliasnumber(s) 132, and user interface(s) 134. In some embodiments, thecomponents of the computing device 104 can include similar capabilitiesand features as discussed in connection with the computing device 102.In some embodiments, the device numbers 130 can be unique to thecomputing device 104, for example, and the device number 130 cancorrespond to a phone number such as “555-111-3333”. In someembodiments, the alias numbers 132 can substantially overlap with thealias numbers 122. For example, and without limitation, the aliasnumbers 132 can correspond to phone numbers such as “555-222-1111”,“555-222-2222”, “555-222-3333”, while the alias numbers 122 cancorrespond to phone numbers such as “555-222-1111” and “555-222-4444”.

The computing appliances 106, 108, and 110 can be any sort of devicecapable of engaging in wired or wireless communication with other,remote devices. Thus, the computing appliances 106, 108, and 110 caninclude, but are not limited to, smart devices such as televisions,refrigerators, washing machines, dryers, smart mirrors, coffee machines,lights, lamps, temperature sensors, music players, headphones, or anyother electronic appliances that can generate, request, receive,transmit, or exchange voice, video, and/or digital data over a network.In some embodiments, the computing appliances 106, 108, and 110 can beconsidered to be a part of the “Internet of Things,” whereby appliancesare enabled to collect and exchange data.

The computing appliance 106 can include a client application 136, aliasnumber(s) 138, and a transfer module 140. In some embodiments, theclient application 136 can be downloaded and installed on the computingappliance 106, and in some embodiments, the client application 136 canbe installed by a manufacturer of the computing appliance 106 andactivated by a user. In some embodiments, the client application 136 cansubstantially correspond to the client application 118, and can enablecommunications at the computing appliance 106 over the alias numbers138. In some embodiments, user interaction with the client application118 on the computing device 102 can enable the alias numbers 138 on thecomputing appliance 106. In some embodiments, the alias numbers 138 cancorrespond to phone numbers that have been selected and enabled forassociation with the computing appliance 106, and can correspond tophone numbers such as “555-222-1111”, “555-222-2222”, “555-222-5555”.That is to say, the alias numbers 138 can overlap with some aliasnumbers associated with various computing devices and computingappliances in the environment 100, and can include alias numbers uniqueto the computing appliance 106. In some embodiments, the alias numbercan include Internet Protocol (IP) addresses, and or other identifiersto identify the computing devices and computing appliances via anetwork.

In some embodiments, the transfer module 140 can include one or moreuser interfaces such as a graphical user interface, various inputdevices (such as a keyboard or remote control device), and/or an audiointerface system. For example, a user can use one or more interfaces ofthe transfer module 140 to initiate communications and/or to initiate orreceive transfers to or from other devices or appliances. In someembodiments, the user interfaces of the transfer module 140 can be usedto select and/or enable the alias numbers 138 to be associated with thecomputing appliance 106.

The computing appliance 108 can include a client application 142, aliasnumber(s) 144, and a transfer module 146. The computing appliance 108can include a client application 148, alias number(s) 150, and atransfer module 152. In some embodiments, the functions and capabilitiesof the computing appliances 106, 108, and 110 can substantiallycorrespond to each other, with respect to the multiple device andmultiple line features discussed herein.

In some embodiments, the alias number 144 can correspond to phonenumbers that have been selected and enabled for association with thecomputing appliance 108, and can correspond to phone numbers such as“555-222-1111”, “555-222-2222”, “555-222-6666”. That is to say, thealias numbers 144 can overlap with some alias numbers associated withvarious computing devices and computing appliances in the environment100, and can include alias numbers unique to the computing appliance108.

In some embodiments, the alias numbers 150 can correspond to phonenumbers that have been selected and enabled for association with thecomputing appliance 110, and can correspond to phone numbers such as“555-222-1111”, “555-222-7777”. That is to say, the alias numbers 150can overlap with some alias numbers associated with various computingdevices and computing appliances in the environment 100, and can includealias numbers unique to the computing appliance 110.

The network provider(s) 112 includes an alias number registration table154 and a device number registration table 156. For example, the aliasnumber registration table 154 can register the various alias numbers inthe environment 100 and associate the alias numbers with one or morecomputing devices 102 and 104 and/or with one or more computingappliances 106, 108, and 110. Further, the alias number registrationtable 154 can include alias numbers that are not yet activated, enabled,or associated with any devices or appliances. In some embodiments, whenan alias number is enabled or activated at the computing device 104, forexample, the computing device 104 can transmit an indication of thealias number registration to the alias number registration table 154,thereby associating a particular alias number with a particularcomputing device.

In some embodiments, the device number registration table 156 canregister the various device numbers in the environment 100 and associatethe device numbers with one or more computing devices 102 and 104 and/orwith one or more computing appliances 106, 108, and 110. In someembodiments, when a device number is enabled or activated at thecomputing appliance 106, for example, the computing appliance 106 cantransmit an indication of the device number registration to the devicenumber registration table 156, thereby associating a particular devicenumber with a particular computing appliance (or computing device). Anexample of the network provider 112 is discussed below in connectionwith FIGS. 2 and 4.

In some embodiments, the network provider 112 can route communicationsover a network using the alias number registration table 154 and/or thedevice number registration table 156. For example, if a call isinitiated at the computing device 102 using the device number 120 (e.g.,“555-111-2222”), the call can be transferred to one or more of the aliasnumbers registered in the alias number registration table 154. Forexample, a user can indicate at the user interface 124 that the call isto be transferred to all devices associated with the alias number“555-222-2222”. In this example, the computing device 102, the computingappliance 106, and the computing appliance 108 are each associated withthe alias number “555-222-2222”, and thus, each of the respectivedevices and appliances would receive an indication of the call to betransferred. For example, the transfer indication can include one ormore audible, visual, and/or haptic indications coupled with a period toreceive input from a user to accept the transfer indication. In someembodiments, the transfer indication may not be outwardly detectable(e.g., by a user), but can provide an indication to a computing deviceor computing appliance that a call is available. In the event thattransfer module 140 accepts the transferred call, the call originatingat the computing device 102 can be transferred to the computingappliance 106, in accordance with embodiments of the disclosure.

FIG. 2 illustrates an example environment 200 in which home monitoringis provided by extending the functionality of the multiple device andmultiple line environment, in accordance with embodiments of thedisclosure.

For example, a monitoring location 202 can include one or moremonitoring components such as components 204, 206, 208, 210, 212, and/or214. In some embodiments, the component 204 can correspond to a videointercom system or a video camera. In some embodiments, the component206 can correspond to a doorbell or a video or audio intercom system. Insome embodiments, the component 208 can correspond to a doorknob and/orremote door lock system. In some embodiments, the component 210 cancorrespond to a sensor for a door, for example, indicating whether thedoor is open or closed. In some embodiments, the component 212 cancorrespond to a sensor for a window, for example, indicating whether thewindow is open or closed. In some embodiments, the component 214 cancorrespond to a motion detector or an infrared sensor. As can beunderstood in the context of this disclosure, the monitoring location202 can include any number of components inside or outside of themonitoring location 202 to sense a variety of conditions and/or tocollect a variety of data.

In some embodiments, the monitoring location 202 can include a computingappliance 216 that can centrally monitor the components 204-214, forexample. In some embodiments, each of the components 204-214 can includean associated computing appliance (such as the computing appliance 216).

The computing appliance 216 can include a client application 218 andalias number(s) 220. In some embodiments, the computing appliance 216can include a transfer module, as illustrated in FIG. 1. In someembodiments, the client application 218 can substantially correspond tothe client application 118 of FIG. 1, for example. That is to say, theclient application 218 can monitor the components 204-214 and can callone or more particular alias numbers 220. In some embodiments,individual components 204-214 can be associated with unique aliasnumbers, such that a first alias number is called based on an indicationfrom the component 204 and a second alias number is called based on anindication from the component 212. In some embodiments, one or morecomponents can be associated with an individual alias number.

Network provider(s) 222 can include a monitoring alert routing module224. In some embodiments, the monitoring alert routing module 224 canreceive calls (i.e., alerts) from the computing appliance 216 and canroute the alert according to one or more rules, preferences, type ofalert, severity of alert, etc. For example, the monitoring alert routingmodule 224 can receive an alert (e.g., a call or a communication) fromthe component 204 (e.g., a video intercom) and can route the alert toone or more computing devices 226, 228, and/or 230 via the network(s)232.

By way of example, in some embodiments, when a door bell is activated(e.g., via the component 206) the computing appliance 216 can call aparticular alias number of the alias numbers 220 associated with thecomponent 206. In some embodiments, the network provider 222 can routethe communication to an individual computing device, simultaneously to aplurality of computing devices, or can cycle through an ordered sequenceof computing devices (e.g., by alerting computing device 226, waitingfor a connection, then alerting computing device 228, waiting for aconnection, and so on). In some embodiments, when the computing device226 receives a communication from the component 206, after a discussionbetween users associated with the devices (e.g., in the case where thecomponent 206 is an intercom system), the computing device 226 cantransmit an indication to the remote door lock (e.g., via the component208) to unlock and/or open the door. As can be understood in the contextof this disclosure, the computing device 226 can transfer thecommunication in accordance with embodiments of the disclosure.

In some embodiments, the network(s) 232 can comprise a mobiletelecommunications network (MTN) configured to implement one or more ofthe second, third, and fourth generation (2G, 3G, and 4G)cellular-wireless access technologies discussed above. Thus, the MTN canimplement GSM, UMTS, and/or LTE/LTE Advanced telecommunicationstechnologies. Further, the network providers 112 and 222 implementingthe GSM, UMTS, LTE, LTE Advanced, and/or HSPA+telecommunicationstechnologies can include, but are not limited to, a combination of: basetransceiver stations BTSs (e.g., NodeBs, Enhanced-NodeBs), Radio NetworkControllers (RNCs), serving GPRS support nodes (SGSNs), gateway GPRSsupport nodes (GGSNs), proxies, a mobile switching center (MSC), amobility management entity (MME), a serving gateway (SGW), a packet datanetwork (PDN) gateway (PGW), an evolved packet data gateway (e-PDG), orany other data traffic control entity configured to communicate,convert, and/or route data packets between the computing devices 102,104, 226, 228, and 230, the computing appliances 106, 108, 110, and 216,and/or the network providers 112 and 222. While FIGS. 1 and 2 illustratethe network providers 112 and 222, it is understood in the context ofthis disclosure that the techniques discussed herein can also beimplemented in other networking technologies, such as nodes that arepart of a wide area network (WAN), metropolitan area network (MAN),local area network (LAN), neighborhood area network (NAN), personal areanetwork (PAN), or the like.

FIG. 3 illustrates an example computing device 300 configured with themultiple device and multiple line functionality, in accordance withembodiments of the disclosure. In some embodiments, the computing device300 can correspond to the computing devices 102, 104, 226, 228, and 230of FIGS. 1 and 2. As illustrated, the computing device 300 comprises amemory 302 storing a native dialer 304, a client application 306, devicenumber(s) 308, alias number(s) 310, user interface(s) 312, a transfermodule 314, an alias permissions module 316, and an alias rules module318. Also, the computing device 300 includes processor(s) 320, aremovable storage 322 and non-removable storage 324, input device(s)326, output device(s) 328, and transceiver(s) 330. In some embodiments,the computing device 300 can include a microphone, a camera, a GPS, anelectronic compass, a heat sensor, biometric sensors, chemical sensors,accelerometer(s), gyroscope(s), pressure sensor(s) and/or photometers.

In various embodiments, memory 302 is volatile (such as RAM),nonvolatile (such as ROM, flash memory, etc.) or some combination of thetwo. The native dialer 304, the client application 306, the devicenumber(s) 308, the alias number(s) 310, the user interface(s) 312, thetransfer module 314, the alias permissions module 316, and the aliasrules module 318 stored in the memory 302 can comprise methods, threads,processes, applications or any other sort of executable instructions.The native dialer 304, the client application 306, the device number(s)308, the alias number(s) 310, the user interface(s) 312, the transfermodule 314, the alias permissions module 316, and the alias rules module318 can also include files and databases.

In some embodiments, the native dialer 304, the client application 306,the device number(s) 308, the alias number(s) 310, the user interface(s)312, and the transfer module 314 can correspond to the native dialer116, the client application 118, the device number(s) 120, the aliasnumber(s) 122, the user interface(s) 124, and the transfer module 140,for example, of FIG. 1. In some embodiments, the module operations inthe computing device 300 can be performed in parallel with the moduleoperations in the network provider 112, for example. In someembodiments, various modules can be used to check the processingdetermined by the other modules.

In some embodiments, the alias permissions module 316 can determinewhether an alias number can be activated or enabled on a variety ofcomputing devices or computing appliances. For example, the aliaspermissions module 316 can activate an alias number at a computingdevice, and can indicate whether other computing devices or computingappliances can be associated with that number. By way of example, a userat the computing device 102 can activate an alias number and canrestrict or otherwise control permissions on which computing devices andcomputing appliances utilize the alias number. In some embodiments, thealias permissions module 316 can include administrative privileges thatcan accept or deny requests to associate an alias number with aparticular device or appliance. For example, the computing appliance 106may initiate an association of a particular alias number with thecomputing appliance 106, while the alias permission module 316 canapprove or deny permission to associate the alias number with thecomputing appliance 106.

In some embodiments, the alias rules module 318 can set rules forcommunicating via one or more alias numbers. For example, the aliasrules module 318 can restrict communications to a particular format(e.g., voice, video, SMS, MMS, etc.), or can determine and enforce rulesindicating a calling order associated with the alias numbers. Forexample, in some embodiments, a rule can determine whether one, some, orall computing devices or computing appliances associated with the aliasnumber can be called simultaneously or serially in a particular order.In some embodiments, the order can be set by the alias rules module 318.

In some embodiments, the processor(s) 320 is a central processing unit(CPU), a graphics processing unit (GPU), or both CPU and GPU, or otherprocessing unit or component known in the art.

The computing device 300 also includes additional data storage devices(removable and/or non-removable) such as, for example, magnetic disks,optical disks, or tape. Such additional storage is illustrated in FIG. 3by removable storage 322 and non-removable storage 324. Tangiblecomputer-readable media can include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information, such as computer readable instructions, datastructures, program modules, or other data. Memory 302, removablestorage 322 and non-removable storage 324 are all examples ofcomputer-readable storage media. Computer-readable storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile discs (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computing device 300. Any such tangible computer-readable media canbe part of the computing device 300.

Computing device 300 can include input device(s) 326, such as a keypad,a cursor control, a touch-sensitive display, a microphone, etc. Also,the computing device 300 can include output device(s) 328, such as adisplay, speakers, etc. These devices are well known in the art and neednot be discussed at length here.

As illustrated in FIG. 3, the computing device 300 can include one ormore wired or wireless transceiver(s) 330. In some wireless embodiments,to increase throughput, the transceiver(s) 330 can utilizemultiple-input/multiple-output (MIMO) technology. The transceiver(s) 330can be any sort of wireless transceivers capable of engaging inwireless, radio frequency (RF) communication. The transceiver(s) 330 canalso include other wireless modems, such as a modem for engaging inWi-Fi, WiMax, Bluetooth, or infrared communication.

FIG. 4 illustrates an example network provider 400 configured to operatein the multiple device and multiple line environment, in accordance withembodiments of the disclosure. In some embodiments, the network provider400 can correspond to the network providers 112 or 222 of FIGS. 1 and 2.It is to be understood in the context of this disclosure that thenetwork provider 400 can be implemented as a single device or as aplurality of devices with modules and data distributed among them. Forexample, an alias number registration table 404, a device numberregistration table 406, a monitoring alert routing module 408, an aliaspermissions module 410, and/or an alias rules module 412 can beimplemented on different devices 400 of the network provider 112. Insome embodiments, the alias number registration table 404, the devicenumber registration table 406, and the monitoring alert routing module408 can correspond to the alias number registration table 154, thedevice number registration table 156, and the monitoring alert routingmodule 224 of FIGS. 1 and 2.

As illustrated, the network provider 400 comprises a memory 402 storingthe alias number registration table 404, the device number registrationtable 406, the monitoring alert routing module 408, the aliaspermissions module 410, and the alias rule modules 412. Also, thenetwork provider 400 includes processor(s) 414, a removable storage 416and non-removable storage 418, input device(s) 420, output device(s)422, and transceiver(s) 424.

In various embodiments, memory 402 is volatile (such as RAM),nonvolatile (such as ROM, flash memory, etc.) or some combination of thetwo. The alias number registration table 404, the device numberregistration table 406, the monitoring alert routing module 408, thealias permissions module 410, and the alias rule module 412 stored inthe memory 402 can comprise methods, threads, processes, applications orany other sort of executable instructions. The alias number registrationtable 404, the device number registration table 406, the monitoringalert routing module 408, the alias permissions module 410, and thealias rules module 412 can also include files and databases. Furtherdescriptions of the alias number registration table 404, the devicenumber registration table 406, and the monitoring alert routing module408 are provided above in connection with the alias number registrationtable 154, the device number registration table 156, and the monitoringalert routing module 224 of FIGS. 1 and 2.

The alias permissions module 410 can determine whether alias numbers canbe activated or enabled on a variety of computing devices or computingappliances. For example, the alias permissions module 410 can activatean alias number at a computing device, and can indicate whether othercomputing devices or computing appliances can be associated with thatnumber. By way of example, a user at the computing device 102 canactivate an alias number and can restrict or otherwise controlpermission on which computing devices and computing appliances utilizethe alias number. In some embodiments, the alias permission module 410can include administrative privileges that can accept or deny requeststo associate an alias number with a particular device or appliance. Forexample, the computing appliance 106 may initiate an association of aparticular alias number with the computing appliance 106, while thealias permissions module 410 can approve or deny permission to associatethe alias number with the computing appliance 106.

The alias rules module 412 can set rules for communicating via one ormore alias numbers. For example, the alias rules module 412 can restrictcommunications to a particular format (e.g., voice, video, SMS, MMS,etc.), or can determine and enforce rules indicating a calling orderassociated with the alias numbers. For example, in some embodiments, arule can determine whether one, some, or all computing devices orcomputing appliances associated with the alias number can be calledsimultaneously or serially in a particular order. In some embodiments,the order can be set by the alias rules module 412.

In some embodiments, the processor(s) 414 is a central processing unit(CPU), a graphics processing unit (GPU), or both CPU and GPU, or otherprocessing unit or component known in the art.

The network provider 400 also includes additional data storage devices(removable and/or non-removable) such as, for example, magnetic disks,optical disks, or tape. Such additional storage is illustrated in FIG. 4by removable storage 416 and non-removable storage 418. Tangiblecomputer-readable media can include volatile and nonvolatile, removableand non-removable media implemented in any method or technology forstorage of information, such as computer readable instructions, datastructures, program modules, or other data. Memory 402, removablestorage 416 and non-removable storage 418 are all examples ofcomputer-readable storage media. Computer-readable storage mediainclude, but are not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile discs (DVD),content-addressable memory (CAM), or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the network provider400. Any such tangible computer-readable media can be part of thenetwork provider 400.

The network provider 400 also can include input device(s) 420, such as akeypad, a cursor control, a touch-sensitive display, a voice inputdevice, etc., and output device(s) 422 such as a display, speakers,printers, etc. These devices are well known in the art and need not bediscussed at length here.

As illustrated in FIG. 4, the network provider 400 also includes one ormore wired or wireless transceiver(s) 424. For example, thetransceiver(s) 424 can include a network interface card (NIC), a networkadapter, a LAN adapter, or a physical, virtual, or logical address toconnect to the network(s) 232, or to the computing devices 102, 104,226, 228, and 230, and/or the computing appliances 106, 108, 110, and216, for example. To increase throughput when exchanging wireless data,the transceivers 424 can utilize multiple-input/multiple-output (MIMO)technology. The transceiver(s) 424 can comprise any sort of wirelesstransceivers capable of engaging in wireless, radio frequency (RF)communication. The transceivers 424 can also include other wirelessmodems, such as a modem for engaging in Wi-Fi, WiMax, Bluetooth

FIGS. 5 and 6 illustrate example processes in accordance withembodiments of the disclosure. These processes are illustrated aslogical flow graphs, each operation of which represents a sequence ofoperations that can be implemented in hardware, software, or acombination thereof. In the context of software, the operationsrepresent computer-executable instructions stored on one or morecomputer-readable storage media that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions include routines, programs, objects,components, data structures, and the like that perform particularfunctions or implement particular abstract data types. The order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the processes.

FIG. 5 illustrates an example process 500 for initiating andtransferring a communication in a multiple device and multiple lineenvironment, in accordance with embodiments of the disclosure.

At 502, the operation can include installing or activating a clientapplication at a computing appliance. In some embodiments, a user candownload a client application to a computing appliance (or computingdevice) via a network. In some embodiments, the client application canbe pre-installed in the computing appliance or computing device and canbe activated to operate in an environment associated with a user.

At 504, the operation can include assigning one or more alias numbers toa computing appliance. In some embodiments, this operation can beperformed at the computing appliance, while in some embodiments, thisoperation can be performed via an administrative interface, such as oneassociated with a computing device. For example, a user (of a computingdevice, for example) can select one or more alias numbers for acomputing appliance and can “push” that assigned alias number to beassociated with the computing appliance. In some embodiments, thisoperation can include an authentication and/or acceptance procedure toverify permissions that the alias number can be associated with aparticular computing appliance and/or computing device.

At 506, the operation can include initiating a communication at a firstcomputing device or a computing appliance. For example, a communicationcan be initiated using a device number or an alias number, and caninclude a voice or video call. This operation can include transmittingone or more requests to the network provider to facilitate thecommunication between communication devices or appliances.

At 508, the operation can include receiving an indication of a transferat the first computing device or the computing appliance. For example,the indication of the transfer (i.e., a transfer indication) can bereceived via a user interface (e.g., a GUI, an audio interface, and/or ahaptic interface), and can indicate a particular alias number, devicenumber, computing device, and/or computing appliance to transfer thecall.

At 510, the operation can include issuing a transfer message to one ormore computing device or computing appliances. For example, the transfermessage can be issued to the computing devices and/or computingappliances identified in the transfer indication in operation 508. Insome embodiments, the transfer message can be issued simultaneously to aplurality of devices, while in some embodiments, the transfer messagecan be issued serially in a particular order associated with one or morerules associated with the alias numbers.

At 512, the operation can include accepting the transfer message at anext computing device or computing appliance. For example, the operation512 can include providing an indication to a user interface associatedwith the next computing device or computing appliance (e.g., the devicefor the call to be transferred). In some embodiments, the acceptance canbe provided via a touchscreen, a remote or button, or voice commands. Insome embodiments, the transfer message can be accepted by only onecomputing device or computing appliance, while in some embodiments, thetransfer message can be accepted by a plurality of devices andappliances. In some embodiments, a transfer can be initiated andcompleted by opening a communication line that is currently being usedfor a communication. For example, if a computing device is communicatingvia a first alias phone number, a computing appliance can open thecommunication channel associated with the first alias phone number toeffectively transfer the call. In some embodiments, the operation 512can include transmitting an acceptance message to the network providerindicating that a computing device or a computing appliance has acceptedthe transfer.

At 514, the operation can include continuing the communication at thenext computing device or computing appliance. For example, when atransfer is complete, the user can experience a seamless transition forcommunicating, in accordance with embodiment of the disclosure.

FIG. 6 illustrates an example process 600 for monitoring a home locationand providing alerts in multiple device and multiple line environment,in accordance with embodiments of the disclosure.

At 602, the operation can include assigning an alias number to amonitoring component. In some embodiments, individual monitoringcomponents can be associated with a unique alias number, while in someembodiments, the alias number associated with the monitoring componentcan be associated with a plurality of monitoring components. In someembodiments, the alias number can be assigned via an interface providedat a computing appliance, a computing device, or a network provider. Insome embodiments, the alias number can be assigned via a centraladministrative page that manages alias number assignments for some orall alias numbers associated with a user account.

At 604, the operation can include determining one or more rulesassociated with the alias number. In some embodiments, the rules caninclude determining a group associated with the alias number, anddetermining an action associated with an alias number, which can bereferred to as operations 606 and 608. A group associated with the aliasnumber can include any additional alias numbers, device numbers,computing devices, and/or computing appliances to be contacted uponreceiving a communication from the monitoring component. An actionassociated with the alias number can include a format of a communicationthat is to be initiated with respect to a particular rule, such as avideo call, a SMS, MMS, etc. In some embodiments, an action can includean order of device numbers and/or alias numbers to contact uponreceiving a communication. In some embodiments, a communication istransmitted and/or initiated simultaneously to associated alias numbersand device numbers, while in some embodiments, the communications areinitiated serially according to the rules defined in the process 600.

At 610, the operation can include receiving an indication from amonitoring component. In some embodiments, the indication can bereceived at a network provider. At 612, the operation can includedetermining an action based at least in part on rules, such as the rulesdefined in the operation 604. At 614, the operation can includeproviding an action to computing device associated with the aliasnumber. In some embodiments, the action can include initiating a videocall or voice call, or sending a SMS or MMS, in accordance with the typeof monitoring component, and the rules as discussed herein. For example,in a case where the monitoring component is a video intercom, the actioncan include establishing a video call with an associated computingdevice. In a case where the monitoring component is a window sensor, theaction can include sending a SMS to an associated computing device whenthe window is opened or closed.

At 616, the operation can include receiving a response from at least onecomputing device associated with the alias number. In some embodiments,the response can include an interaction including a voice or video call.In some embodiments, the response can include a command directed to amonitoring component to open a remote door lock, for example. In someembodiments, the response can include a command to control a computingappliance associated with one or more alias numbers. In someembodiments, the response can include a request to transfer the call toanother computing device or computing appliance.

CONCLUSION

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claims.

What is claimed is:
 1. A system, comprising: one or more processors; amemory; and one or more modules stored in the memory and executable bythe one or more processors to perform operations comprising:associating, by a network provider, a device phone number with awireless computing device; receiving a first indication from thewireless computing device to associate an alias phone number with thewireless computing device; receiving a second indication from thewireless computing device to associate the alias phone number with acomputing appliance; receiving a first request to initiate a voice callat the wireless computing device using the device phone numberassociated with the wireless computing device; receiving a secondrequest to initiate a transfer of the voice call from the device phonenumber to the alias phone number; transmitting a transfer message to thecomputing appliance; and transferring the voice call from the wirelesscomputing device using the device phone number to the computingappliance using the alias phone number.
 2. The system of claim 1,wherein the device phone number is associated with an InternationalMobile Subscriber Identity (IMSI).
 3. The system of claim 1, wherein thealias phone number is one of a plurality of alias phone numbersassociated with a user account, the user account associated with thewireless computing device.
 4. The system of claim 1, wherein theoperations further comprise transmitting the transfer message to aplurality of computing appliances associated with the alias phonenumber.
 5. A system, comprising: one or more processors; a memory; andone or more modules stored in the memory and executable by the one ormore processors to perform operations comprising: receiving, from acomputing device associated with a network provider, a first request toplace a call from a device number associated with the computing device;receiving, from the computing device, a second request to transfer thecall to an alias number, the second request indicating the alias number;in response to receiving the second request, determining one or morecomputing appliances associated with the alias number; transmitting, tothe one or more computing appliances, a transfer message indicating thecall is to be transferred to the one or more computing appliances;receiving, from a computing appliance of the one or more computingappliances, an acceptance of the transfer message based on user inputreceived at the computing appliance; and transferring the call to thecomputing appliance in response to the acceptance.
 6. The system ofclaim 5, wherein the determining the one or more computing devicesassociated with the alias number comprises accessing an alias numberregistration table at the network provider.
 7. The system of claim 5,wherein a plurality of alias numbers are associated with the computingdevice, wherein ones of the plurality of alias numbers are enabled onthe computing device via a user interface.
 8. The system of claim 5,wherein the operations further comprise registering the alias numberwith the computing appliance at an alias number registration table atthe network provider.
 9. The system of claim 5, wherein the computingdevice is a wireless phone and wherein the computing appliance isselected from a group comprising a television, a refrigerator, a washingmachine, or a smart mirror.
 10. The system of claim 5, wherein theoperations further comprise allocating a plurality of alias numbers to auser account, the user account associated with the computing device. 11.The system of claim 5, wherein the operations further comprise receivingan assignment of the alias number to the computing appliance, theassignment received from the computing device at the network provider.12. The system of claim 5, wherein the device number is associated withan International Mobile Subscriber Identity (IMSI) provided by thenetwork provider.
 13. The system of claim 5, wherein the operationsfurther comprise transmitting the transfer message substantiallysimultaneously to the one or more computing appliances associated withthe alias number.
 14. The system of claim 5, wherein the operationsfurther comprise enabling a client application to operate at thecomputing appliance, the client application associated with one or morealias numbers and configured to receive input from a user at thecomputing appliance.
 15. A computer-implemented method performed by oneor more processors configured with specific instructions, thecomputer-implemented method comprising: receiving, from a computingdevice associated with a network provider, a first request to place acall from a device number associated with the computing device;receiving, from the computing device, a second request to transfer thecall to an alias number, the second request indicating the alias number;in response to receiving the second request, determining one or morecomputing appliances associated with the alias number; transmitting, tothe one or more computing appliances, a transfer message indicating thecall is to be transferred to the one or more computing appliances;receiving, from a computing appliance of the one or more computingappliances, an acceptance of the transfer message based on user inputreceived at the computing appliance; and transferring the call to thecomputing appliance in response to the acceptance.
 16. Thecomputer-implemented method of claim 15, further comprising registeringthe alias number with the computing appliance at an alias numberregistration table at the network provider.
 17. The computer-implementedmethod of claim 15, further comprising allocating a plurality of aliasnumbers to a user account, the user account associated with thecomputing device.
 18. The computer-implemented method of claim 15,further comprising receiving an assignment of the alias number to thecomputing appliance, the assignment received from the computing deviceat the network provider.
 19. The computer-implemented method of claim15, further comprising transmitting the transfer message substantiallysimultaneously to the one or more computing appliances associated withthe alias number.
 20. The computer-implemented method of claim 15,wherein a plurality of alias numbers are associated with the computingdevice, wherein ones of the plurality of alias numbers are enabled onthe computing device via a user interface.